| title | author | date | source | notoc |
|---|---|---|---|---|
LDAP Search Filter Cheatsheet |
Jon LaBelle |
January 4, 2021 |
true |
Discover gists
| [Adblock Plus 1.1] | |
| wikipedia.org##.nag-trigger | |
| wikipedia.org###centralNotice | |
| wikipedia.org##[id$=“banner-nag”] |
You can use the below link to access Fritzing downloads for free.
Additionally, below are direct download links to Fritzing.
- Copy content of
vsix-bookmarklet, create a bookmark in your browser. - Navigate to the web page of the VS Code extension you want to install.
- Click the bookmark you just created, then click the download button.

- After download finished, rename the file extension to
*.vsix. - In VS Code, select Install from VSIX... in the extension context menu.

| #!/usr/bin/env bash | |
| # Name: gam-archive.sh | |
| # Usage: gam-archive.sh email_prefix [mail|drive|both] | |
| # Example: gam-archive.sh jsmith mail | |
| # Description: This script will archive a Google Workspace account's email (as .mbox) and/or Google Drive files to a specified Google Drive folder. | |
| # Author: Zoë Kelly (zoe@starshade.ca), Kim Nilsson (github@no-substitute.com) | |
| # License: MIT | |
| # Created: 2020 | |
| # Updated: 2022-07-19 | |
| ## Note: Depending on the export size and your upload speed, it could take 10 minutes or longer for each archival. |
It turns out that MacOS Tahoe can generate and use secure-enclave backed SSH keys! This replaces projects like https://github.com/maxgoedjen/secretive
There is a shared library /usr/lib/ssh-keychain.dylib that traditionally has been used to add smartcard support
to ssh by implementing PKCS11Provider interface. However since recently it also implements SecurityKeyProivder
which supports loading keys directly from the secure enclave! SecurityKeyProvider is what is normally used to talk to FIDO2 devices (e.g. libfido2 can be used to talk to your Yubikey). However you can now use it to talk to your Secure Enclave instead!
A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.
| ### Simple transient prompt | |
| [[ -c /dev/null ]] || return | |
| zmodload zsh/system || return | |
| ## Set the transient prompt PROMPT here - | |
| TRANSIENT_PROMPT='%# ' # Sample value | |
| function set_prompt { | |
| ## Set the values of PROMPT and RPROMPT here |
Applied rationality for a coding agent. Defensive epistemology: minimize false beliefs, catch errors early, avoid compounding mistakes.
This is correct for code, where:
- Reality has hard edges (the compiler doesn't care about your intent)
- Mistakes compound (a wrong assumption propagates through everything built on it)
- The cost of being wrong exceeds the cost of being slow
| // ignore_for_file: cascade_invocations, omit_local_variable_types, prefer_asserts_with_message, public_member_api_docs // to make it easier to compare with Flutter SDK code after every major release | |
| import 'dart:math'; | |
| import 'package:flutter/widgets.dart'; | |
| /// Use this class to define an inset box shadow that can be used inside the [InsetShadowShapeDecoration] shadows. | |
| final class InsetBoxShadow extends BoxShadow { | |
| const InsetBoxShadow({ | |
| super.color, |